Skip to content

Update the OWASP Top 10 page to the 2025 version - #225

Merged
jgadsden merged 1 commit into
OWASP:mainfrom
cvas22:update/top-ten-2025
Nov 11, 2026
Merged

jgadsden merged 1 commit into
OWASP:mainfrom
cvas22:update/top-ten-2025

Conversation

@cvas22

@cvas22 cvas22 commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Summary :

The Foundations page on the OWASP Top 10 still describes the 2021 list, while the 2025 version is out. This updates every category to 2025: the new order, the renamed categories (Authentication Failures, Software or Data Integrity Failures, Security Logging and Alerting Failures), Software Supply Chain Failures replacing Vulnerable and Outdated Components, SSRF moving into Broken Access Control, and the new A10 Mishandling of Exceptional Conditions. It also adds a short note on what changed from 2021.

The cheat sheet index only has 2021 anchors, so each category now links the relevant cheat sheets directly. I kept the existing text wherever it still applies.

I couldn't find an issue for this, happy to open one if you'd like it tracked that way.

Description for the changelog :

Update the OWASP Top 10 page to the 2025 version

Declaration:

Thanks for submitting a pull request, please make sure:

  • content meets the license for this project
  • you have read the contribution guide
    and agree to the Code of Conduct
  • either no AI-generated content has been used in this pull request
  • or any use of AI
    in this pull request has been disclosed below:
    Claude Code with model Opus 5.5 was used to assist in building this PR. I used it to update the outdated page (from 2021 to 2025).

Other info :

Category names, order and the changes from 2021 are taken from the Top 10 2025 introduction and category pages, and all new links resolve. All content was edited, checked and human reviewed before finalizing this PR. If you have any questions, please leave a message. Thx

@jgadsden

Copy link
Copy Markdown
Contributor

Hello @cvas22 , could you be sure to read the contribution guide and the Code of Conduct, in particular the use of generative AI

@cvas22
cvas22 marked this pull request as ready for review November 10, 2026 21:42
@cvas22

cvas22 commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor Author

@jgadsden Updated PR in accordance with the guidelines under contributing. All content was human reviewed, human edited, and human checked to ensure it does what it claims it does in an efficient manner. Please leave a message if you'd like anything else from me. Thx.

@jgadsden jgadsden left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for this pull request @cvas22
The use of AI is acceptable in the changes made here; they read well and this is a useful addition
There is no need to retrospectively create an issue for this, although this is against the contributors guidelines it can justified for these changes

@jgadsden
jgadsden merged commit e48421a into OWASP:main Nov 11, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants